@mitu thanks, I'll try it!

@StevenRice I'm surprised that Retroarch doesn't already do this. I've been thinking about getting one of the new Brawler64s for this very purpose.

@ShmashBroJoe with N64 the "A" is the normal spot for the "B" , which is the south of the controller. The "B" is the normal spot for the "Y" which is the west of the controller. It is set up the same directions as the original N64

@adamg thanks for sharing this. I just updated to Buster and my old fix for mapping the generic n64 didn't work. Mapping a hotkey for the menu did the trick. Weird though, I only had to map my A and Z buttons, everything worked fine.

@billymild said in Button mapping not working for lr-parallel-n64:

Is there a way to manually check the ParallelN64 emulator itself? Is there a way to access the retroarch menu from a Keyboard?

Use F1 on the keyboard to open the RetroArch's RGUI menu, then you can check the mappings in the Controller section.

@akr8080 Some controllers don't expose the turbo button, but internally activate the turbo feature when you press it along with the other button where the turbo function is applied. Maybe the Brawler64 is similar, but can't find a manual for the controller to confirm.

@bootmonster said in I have a question for anyone who has purchased a NINTENDO 64 controller.:

Not sure where the mixed messages have come from on that but can confirm it works perfectly.

https://i.reddit.com/r/n64/comments/qkn95i/nso_n64_controller_issues/ https://i.reddit.com/r/n64/comments/qjcrvr/my_experience_with_bluetooth_and_nso_controller/ https://i.reddit.com/r/RetroArch/comments/qj8w91/nintendo_64_nso_controller_phantom_inputs_on/

@sleve_mcdichael said in N64 Controller Input Config:

The autoconfig only works for libretro cores;

Actually, the auto-config works for a few other emulators also, including Mupen64Plus (see here).

@Jay420 Please provide the info requested in https://retropie.org.uk/forum/topic/3/read-this-first, which should include the emulator you're using and what controller type do you have.

@toigo Solution to this problem is at https://retropie.org.uk/forum/topic/29481/controls-randomly-locked-for-1-or-2-secs/11 (switching to HDMI audio in raspi-config).

@ringus said in Changed n64 controller and mapping is busted:

mupen64plus-glideN64-highres

This is the standalone emulator, as @retropieuser555 mentioned, with a different video plugin. In addition to the standalone emulator, there are 2 separate libretro based emulator (lr-mupen64plus and lr-mupen64plus-next) which should be configured automatically based on your Controller configuration with the mapping explained on the same page that was mentioned by @retropieuser555.

@mitu It worked, thank you!

@rip I had the very same issue and could not find any good solution posted already so I will post mine here (Z button was never an issue for me , Z button is also my hotkey)

Once configured as screenshot above and after first launch with n64 emu the following configuration was generated into /opt/retropie/configs/n64/InputAutoCfg.ini

; SWITCH CO.,LTD. Controller (Dinput)_START [SWITCH CO.,LTD. Controller (Dinput)] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = C Button U = button(9) L Trig = button(4) C Button D = button(1) button(0) #C Down gets mapped to button(1) which is really B Button and button(0) is the actual C Down button DPad U = hat(0 Up) DPad L = hat(0 Left) C Button L = button(3) Y Axis = axis(1-,1+) X Axis = axis(0-,0+) DPad R = hat(0 Right) Z Trig = button(6) C Button R = button(8) R Trig = button(5) DPad D = hat(0 Down) Start = button(12) A Button = button(2) # Lack of mapping for button B at all ; SWITCH CO.,LTD. Controller (Dinput)_END

I then used jtest to actually view which button was what hence my conclusions above with jstest /dev/input/js0 then I edited the file nano /opt/retropie/configs/n64/InputAutoCfg.ini with the following

; SWITCH CO.,LTD. Controller (Dinput)_START [SWITCH CO.,LTD. Controller (Dinput)] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = C Button U = button(9) L Trig = button(4) C Button D = button(0) DPad U = hat(0 Up) DPad L = hat(0 Left) C Button L = button(3) Y Axis = axis(1-,1+) X Axis = axis(0-,0+) DPad R = hat(0 Right) Z Trig = button(6) C Button R = button(8) R Trig = button(5) DPad D = hat(0 Down) Start = button(12) A Button = button(1) B Button = button(2) ; SWITCH CO.,LTD. Controller (Dinput)_END

Hope this might help someone else with same setup, cheers

/a

For future reference, I managed to solve my issue by going into the RGUI going to Quick Menu > Controls and playing with those settings. Make sure to save those settings as a game remap file and do not select save on exit as this would break retroarch.cfg files.

@Dr-Nick

Start with this youtube video:

This will help. If you still have questions, come back. I'll keep an eye on the thread.

D

For other folks looking for answers about this, see the following forum:

https://retropie.org.uk/forum/topic/27007/button-mapping-for-a-real-n64-controller?_=1594477474831

@DavidDraper I'm sorry to hear that it is not working for you.

First off, you definitely shouldn't edit the .bak file, stick with only the .cfg file. Sorry if I wasn't clear there. I'm not sure what the .bak even does, or how to revert it.

Second, remember to only overwrite the button mappings. For example, in the .cfg file there are 2 lines above the mappings that I left intact. For me it reads:
input_device = "SealieComputing N64 RetroPort"
input_driver = "udev"

This of course would change depending on what controller you are using.

If you've done all of the above correctly, then the only other thing that I can think of is that it might be because you are using a "Generic USB" controller rather than an original N64 controller with an adapter.
Perhaps this means your buttons are in a different order, or are labeled differently, I'm not really sure as I don't own a Dragon Rise controller to test with.

Still, if you'd like, feel free to copy what your original dragon rise.cfg file was (prior to copy / pasting my info), and I'll see if I can translate it into something that may work for you.

Otherwise, good luck, and I hope that other solution works for you!

Anybody help me?;)

@mitu Thank you!!